PreviousNextTracker indexSee it online !

(171/185) 382 - Console/Errorlist: Extra lines regexp

Feature request:

1.) Make "Extra lines regexp" create "Filename", "Line number" and "Error message" like "Error Regexp" and display this accordingly in ErrorList. Clicking on the extra line in Error List should make the cursor jump to that file and line.

2.) Warnings should be handled the same way: Warnings should allow "extra lines" (colored and listed as Warnings, not as Errors; clickable)

For me, it would be sufficient:
* Using the same Extra Line Regexp for Errors and Warnings
* Using the same "Filename", "Line number" and "Error message" entry for all (e.g. $1, $2, $3)

Thus, plugins options UI of Console needs no changes.


--- Details below ---

Errormessages of Ruby look like this, in the Console Window (contrived):

~~~
D:/Test/simple_trx_ui.rb :761:in `on_run_single_test': undefined local
<no line break here>
variable or method `test_end' for #<SimpleTrxUi:0x2c8c54c> (NameError)
from D:/Test/simple_trx_ui.rb :876:in `eval'
from D:/Test/simple_trx_ui.rb :761:in `on_run_single_test'
from D:/Test/trx/external/highline.rb:309:in `choose'
from D:/Test/simple_trx_ui.rb :918:in `new'
from D:/Test/simple_trx_ui.rb :918
Process ruby exited with code 1
~~~

Warningmessages are the same, despite "NameError" is replaced by "...Warning". The "from"-lines of Warnings are exactly the same es of Errors.

Up to now, as a work around, I handle warning-messages as error-messages and each line as a separate error. But with a lot of lines with error- and warning-messages it becomes very bulky and I would like to separate Warnings from Errors.

I'm using:
~~~
* Windows 8.1
* jEdit 5.3pre1
* Java 1.8.0_91
* Console 5.1.4
* ErrorList 2.3
~~~

Submitted axelnbg - 2017-02-12 10:58:06.897000 Assigned
Priority 5 Labels
Status open Group None
Resolution None

Comments

2018-02-27 14:27:07.023000
ezust

The code for handling regexes in the output is very old and not written by me.
To change it would require very thorough testing against existing regexes and error outputs.
We do not have any automated regression tests made up for this but I think that would help.